Route Java worker startup through an app registry#390
Merged
Conversation
THardy98
force-pushed
the
feat/java-worker-app-registry
branch
3 times, most recently
from
53a0a58 to
b2b058a
Compare
Sushisource
approved these changes
Jun 1, 2026
The Java worker now follows the reorganized worker shape: the registry dispatches app entrypoints, and the harness lives in the root worker project instead of a separate Gradle subproject.
THardy98
force-pushed
the
feat/java-worker-app-registry
branch
from
b2b058a to
a2f9a0c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
Effectively the Java port of:
#366 (typescript)
and
#358 (go)
Why?
Same benefits:
workers/javapackage, code reduction